Systems and methods for automated house damage detection and reporting

ABSTRACT

A system for automated house damage detection and reporting may comprise at least one subsystem configured for receiving a damage detection signal detecting potential damage to a building from at least one sensor operably connected to the building, and at least one subsystem configured for automatically communicating damage detection data using the received damage detection signal to a remote system outside the building for further analysis.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/362,136, filed Jan. 31, 2012, now U.S. Pat. No. 8,400,299, which is acontinuation of U.S. patent application Ser. No. 12/492,437, filed onJun. 26, 2009, now U.S. Pat. No. 8,106,769, which is herein incorporatedby reference.

BACKGROUND

Smart house functionality is a maturing space, but the opportunity forinsurance companies remains largely untapped. Currently, there are notruly useful early warning and loss mitigation systems that actuallysave costs and time for both the homeowner and insurance company alike.Currently, homeowners insurance claim events are detected by thehomeowner, and they contact their insurance company to inform them thatthere has been a loss. However, further loss could be mitigated withautomated warning and detection systems that interface with theinsurance company systems. For example, homeowners may often neverbecome aware of minor to medium hail damage to their roofs until suchtime as that damage leads to further water damage. If they could be madeaware of such loss events earlier and then take corrective actions, thenthe increased damage and loss could have been mitigated.

In this regard, there is a need for systems and methods that overcomethe shortcomings described above and others.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

In consideration of the above-identified shortcomings of the art,systems and methods for automated house damage detection and reportingare described herein. For several embodiments, a system automated housedamage detection and reporting may comprise at least one subsystemconfigured for receiving a damage detection signal detecting potentialdamage to a building from at least one sensor operably connected to thebuilding, and at least one subsystem configured for automaticallycommunicating damage detection data using the received damage detectionsignal to a remote system outside the building for further analysis.

Other features and embodiments are described below.

BRIEF DESCRIPTION OF THE DRAWINGS

Systems and methods for automated house damage detection and reportingare further described with reference to the accompanying drawings inwhich:

FIG. 1 is a block diagram representing an exemplary computingenvironment suitable for use in conjunction with implementing systemsand methods for automated house damage detection and reporting;

FIG. 2 illustrates an exemplary networked computing environment in whichmany computerized processes may be implemented to perform providingautomated house damage detection and reporting;

FIG. 3 is a partial, cross-sectional elevation view of an example houseroof having a hail damage detection system in accordance with systemsand methods for automated house damage detection and reporting;

FIG. 4 is a block diagram illustrating an example system within a housefor automated house damage detection and reporting;

FIG. 5 is a block diagram illustrating a portion of an example systemextending outside the house for automated house damage detection andreporting;

FIG. 6 is a flow chart illustrating an example process within the housefor automated house damage detection and reporting; and

FIG. 7 is a flow chart illustrating an example process for automatedhouse damage detection and reporting to an insurance company.

DETAILED DESCRIPTION

Certain specific details are set forth in the following description andfigures to provide a thorough understanding of various embodiments.Certain well-known details often associated with computing and softwaretechnology are not set forth in the following disclosure to avoidunnecessarily obscuring the various embodiments. Further, those ofordinary skill in the relevant art will understand that they canpractice other embodiments without one or more of the details describedbelow. Finally, while various methods are described with reference tosteps and sequences in the following disclosure, the description as suchis for providing a clear implementation of various embodiments, and thesteps and sequences of steps should not be taken as required to practicethe embodiments.

Referring next to FIG. 1, shown is a block diagram representing anexemplary computing environment suitable for use in conjunction withimplementing the processes described below. For example, thecomputer-executable instructions that carry out the processes andmethods for automated house damage detection and reporting may resideand/or be executed in such a computing environment as shown in FIG. 1.The computing environment 220 is only one example of a suitablecomputing environment and is not intended to suggest any limitation asto the scope of use or functionality of the embodiments. Neither shouldthe computing environment 220 be interpreted as having any dependency orrequirement relating to any one or combination of components illustratedin the exemplary computing environment 220. For example a mobile devicemay also include one or more items such as those described below for usein conjunction with implementing the processes described below.

Aspects of the embodiments are operational with numerous other generalpurpose or special purpose computing environments or configurations.Examples of well known computing systems, environments, and/orconfigurations that may be suitable for use with the embodimentsinclude, but are not limited to, personal computers, server computers,hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

Aspects of the embodiments may be implemented in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Aspects ofthe embodiments may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices.

An exemplary system for implementing aspects of the embodiments includesa general purpose computing device in the form of a computer 241.Components of computer 241 may include, but are not limited to, aprocessing unit 259, a system memory 222, a graphics interface 231, agraphics processing unit (GPU) 229, video memory 230, video interface232 and a system bus 221 that couples various system componentsincluding the system memory 222 to the processing unit 259. The systembus 221 may be any of several types of bus structures including a memorybus or memory controller, a peripheral bus, and a local bus using any ofa variety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus also known as Mezzanine bus.

Computer 241 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 241 and include both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media include both volatileand nonvolatile, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules or other data.Computer storage media include, but are not limited to, random accessmemory (RAM), read-only memory (ROM), Electrically Erasable ProgrammableRead-Only Memory (EEPROM), flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other medium which can be used to storethe desired information and which can accessed by computer 241. By wayof example, and not limitation, communication media include wired mediasuch as a wired network or direct-wired connection, and wireless mediasuch as acoustic, radio frequency (RE), infrared and other wirelessmedia. Combinations of the any of the above should also be includedwithin the scope of computer readable media.

The system memory 222 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as ROM 223 and RAM 260. A basicinput/output system (BIOS) 224, containing the basic routines that helpto transfer information between elements within computer 241, such asduring start-up, is typically stored in ROM 223. RAM 260 typicallycontains data and/or program modules that are immediately accessible toand/or presently being operated on by processing unit 259. By way ofexample, and not limitation, FIG. 1 illustrates operating system 225,application programs 226, other program modules 227, and program data228.

The computer 241 may also include other removable/non-removable,volatile/nonvolatile computer storage media. By way of example only,FIG. 1 illustrates a hard disk drive 238 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 239that reads from or writes to a removable, nonvolatile magnetic disk 254,and an optical disk drive 240 that reads from or writes to a removable,nonvolatile optical disk 253 such as a CD-ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 238 is typically connectedto the system bus 221 through a non-removable memory interface such asinterface 234, and magnetic disk drive 239 and optical disk drive 240are typically connected to the system bus 221 by a removable memoryinterface, such as interface 235.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 1 provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 241. In FIG. 1, for example, hard disk drive 238 is illustratedas storing operating system 258, application programs 257, other programmodules 256, and program data 255. Note that these components can eitherbe the same as or different from operating system 225, applicationprograms 226, other program modules 227, and program data 228. Operatingsystem 258, application programs 257, other program modules 256, andprogram data 255 are given different numbers here to illustrate that, ata minimum, they are different copies. A user may enter commands andinformation into the computer 241 through input devices such as akeyboard 251 and pointing device 252, commonly referred to as a mouse,trackball or touch pad. Other input devices (not shown) may include amicrophone, joystick, game pad, satellite dish, scanner, or the like.These and other input devices are often connected to the processing unit259 through a user input interface 236 that is coupled to the system bus221, but may be connected by other interface and bus structures, such asa parallel port, game port or a universal serial bus (USB). A monitor242 or other type of display device is also connected to the system bus221 via an interface, such as a video interface 232. In addition to themonitor 242, computer 241 may also include other peripheral outputdevices such as speakers 244 and printer 243, which may be connectedthrough an output peripheral interface 233.

The computer 241 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer246. The remote computer 246 may be a personal computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto the computer 241, although only a memory storage device 247 has beenillustrated in FIG. 1. The logical connections depicted in FIG. 1include a local area network (LAN) 245 and a wide area network (WAN)249, but may also include other networks. Such networking environmentsare commonplace in offices, enterprise-wide computer networks, intranetsand the Internet.

When used in a LAN networking environment, the computer 241 is connectedto the LAN 245 through a network interface or adapter 237. When used ina WAN networking environment, the computer 241 typically includes amodern 250 or other means for establishing communications over the WAN249, such as the Internet. The modern 250, which may be internal orexternal, may be connected to the system bus 221 via the user inputinterface 236, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 241, orportions thereof, may be stored in the remote memory storage device 247.By way of example, and not limitation, FIG. 1 illustrates remoteapplication programs 248 as residing on the remote memory storage device247. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers may be used.

It should be understood that the various techniques described herein maybe implemented in connection with hardware or software or, whereappropriate, with a combination of both. As used herein a “system” or“subsystem” may comprise one or more of or any combination of, thefollowing: mechanical devices, hardware, components of hardware,circuits, circuitry, logic design, logical components, software,software modules, components of software or software modules, softwareprocedures, software instructions, software routines, software objects,software functions, software classes, software programs, filescontaining software, etc., to perform the intended function of thesystem or subsystem. Thus, the methods and apparatus of the embodiments,or certain aspects or portions thereof, may take the form of programcode (i.e., instructions) embodied in tangible media, such as floppydiskettes, CD-ROMs, hard drives, or any other machine-readable storagemedium wherein, when the program code is loaded into and executed by amachine, such as a computer, the machine becomes an apparatus forpracticing the embodiments. In the case of program code execution onprogrammable computers, the computing device generally includes aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. One or more programs thatmay implement or utilize the processes described in connection with theembodiments, e.g., through the use of an application programminginterface (API), reusable controls, or the like. Such programs arepreferably implemented in a high level procedural or object-orientedprogramming language to communicate with a computer system. However, theprogram(s) can be implemented in assembly or machine language, ifdesired. In any case, the language may be a compiled or interpretedlanguage, and combined with hardware implementations.

Although exemplary embodiments may refer to utilizing aspects of theembodiments in the context of one or more stand-alone computer systems,the embodiments are not so limited, but rather may be implemented inconnection with any computing environment, such as a network ordistributed computing environment. Still further, aspects of theembodiments may be implemented in or across a plurality of processingchips or devices, and storage may similarly be effected across aplurality of devices. Such devices might include personal computers,network servers, handheld devices, supercomputers, or computersintegrated into other systems such as automobiles and airplanes.

Referring next to FIG. 2, shown is an exemplary networked computingenvironment in which many computerized processes may be implemented toperform the processes described below. For example, distributed orparallel computing may be part of such a networked environment withvarious clients on the network of FIG. 2 using and/or implementingsystems and methods for automated house damage detection and reporting.One of ordinary skill in the art can appreciate that networks canconnect any computer or other client or server device, or in adistributed computing environment. In this regard, any computer systemor environment having any number of processing, memory, or storageunits, and any number of applications and processes occurringsimultaneously is considered suitable for use in connection with thesystems and methods provided.

Distributed computing provides sharing of computer resources andservices by exchange between computing devices and systems. Theseresources and services include the exchange of information, cachestorage and disk storage for files. Distributed computing takesadvantage of network connectivity, allowing clients to leverage theircollective power to benefit the entire enterprise. In this regard, avariety of devices may have applications, objects or resources that mayimplicate the processes described herein.

FIG. 2 provides a schematic diagram of an exemplary networked ordistributed computing environment. The environment comprises computingdevices 271, 272, 276, and 277 as well as objects 273, 274, and 275, anddatabase 278. Each of these entities 271, 272, 273, 274, 275, 276, 277and 278 may comprise or make use of programs, methods, data stores,programmable logic, etc. The entities 271, 272, 273, 274, 275, 276, 277and 278 may span portions of the same or different devices such as PDAs,audio/video devices, MP3 players, personal computers, etc. Each entity271, 272, 273, 274, 275, 276, 277 and 278 can communicate with anotherentity 271, 272, 273, 274, 275, 276, 277 and 278 by way of thecommunications network 270. In this regard, any entity may beresponsible for the maintenance and updating of a database 278 or otherstorage element.

This network 270 may itself comprise other computing entities thatprovide services to the system of FIG. 2, and may itself representmultiple interconnected networks. In accordance with aspects of theembodiments, each entity 271, 272, 273, 274, 275, 276, 277 and 278 maycontain discrete functional program modules that might make use of anAPI, or other object, software, firmware and/or hardware, to requestservices of one or more of the other entities 271, 272, 273, 274, 275,276, 277 and 278.

It can also be appreciated that an object, such as 275, may be hosted onanother computing device 276. Thus, although the physical environmentdepicted may show the connected devices as computers, such illustrationis merely exemplary and the physical environment may alternatively bedepicted or described comprising various digital devices such as PDAs,televisions, MP3 players, etc., software objects such as interfaces, COMobjects and the like.

There are a variety of systems, components, and network configurationsthat support distributed computing environments. For example, computingsystems may be connected together by wired or wireless systems, by localnetworks or widely distributed networks. Currently, many networks arecoupled to the Internet, which provides an infrastructure for widelydistributed computing and encompasses many different networks. Any suchinfrastructures, whether coupled to the Internet or not, may be used inconjunction with the systems and methods provided.

A network infrastructure may enable a host of network topologies such asclient/server, peer-to-peer, or hybrid architectures. The “client” is amember of a class or group that uses the services of another class orgroup to which it is not related. In computing, a client is a process,i.e., roughly a set of instructions or tasks, that requests a serviceprovided by another program. The client process utilizes the requestedservice without having to “know” any working details about the otherprogram or the service itself. In a client/server architecture,particularly a networked system, a client is usually a computer thataccesses shared network resources provided by another computer, e.g., aserver. In the example of FIG. 2, any entity 271, 272, 273, 274, 275,276, 277 and 278 can be considered a client, a server, or both,depending on the circumstances.

A server is typically, though not necessarily, a remote computer systemaccessible over a remote or local network, such as the Internet. Theclient process may be active in a first computer system, and the serverprocess may be active in a second computer system, communicating withone another over a communications medium, thus providing distributedfunctionality and allowing multiple clients to take advantage of theinformation-gathering capabilities of the server. Any software objectsmay be distributed across multiple computing devices or objects.

Client(s) and server(s) communicate with one another utilizing thefunctionality provided by protocol layer(s). For example, HyperTextTransfer Protocol (HTTP) is a common protocol that is used inconjunction with the World Wide Web (WWW), or “the Web.” Typically, acomputer network address such as an Internet Protocol (IP) address orother reference such as a Universal Resource Locator (URL) can be usedto identify the server or client computers to each other. The networkaddress can be referred to as a URL address. Communication can beprovided over a communications medium, e.g., client(s) and server(s) maybe coupled to one another via TCP/IP connection(s) for high-capacitycommunication.

In light of the diverse computing environments that may be builtaccording to the general framework provided in FIG. 2 and the furtherdiversification that can occur in computing in a network environmentsuch as that of FIG. 2, the systems and methods provided herein cannotbe construed as limited in any way to a particular computingarchitecture. Instead, the embodiments should be construed in breadthand scope in accordance with the appended claims.

Referring next to FIG. 3 shown is a partial, cross-sectional elevationview of an example house roof having a hail damage detection system inaccordance with systems and methods for automated house damage detectionand reporting. For example, the roof 301 may comprise a substrate layer305 with a plurality of shingles 303 layered on top of the substrate305. Below the substrate are one or more sensors 307 309 that areoperable for detecting an impact on the roof (e.g., from a hail stone245). The sensors are attached under the roof 301 such that an impact ontop of the roof over a certain pressure, for example, over a specificpounds per square inch (psi), are detected by the sensors 307 309. Thesensors 307 309 may be placed throughout the entire roof 301 or within aparticular section or sections of the roof. Also, the sensors 307 309may be calibrated according to the particular strength or thickness ofthe materials of which the roof 301 is comprised. For example, if theroof 301 is a composite roof instead of a shingle roof, the sensors 307309 may be arranged and/or calibrated to detect a larger or smallerimpacts as necessary. Also, the sensors may be placed under especiallysensitive areas of the roof such as under skylights within the roof orunder solar panels on the roof 301. Although there are only two examplesensors 307 309 shown in FIG. 3, any number of sensors may be used as isappropriate for the particular application, cost limitations and roofconditions.

Referring next to FIG. 4, shown is a block diagram illustrating anexample system within a house for automated house damage detection andreporting. Shown is an example sensor 307, sensor body, circuitry, andpower 401, sensor mounts 403 for mounting of the sensor under a roof,and a sensor antenna 405. Within the sensor body, there is circuitrythat is operable for detecting and measuring impact on an impact plateof the sensor, for example. The antenna is operable for wirelesslycommunicating data generated by the sensor circuitry 401 regarding oneor more detected impacts to a receiving unit 407. The receiving unit 407having an operable antenna 409 may be located within the house in whichthe sensors are installed, for example, and is operable for collecting,interpreting and translating the data generated by the sensor circuitry401 of one or more sensors 307 and then re-transmitting the collectedtranslated data to another location such as an insurance company, bank,or the resident of the house for further analysis. The collectedtranslated data may be communicated from the receiving unit 407 over anynumber of suitable communication channels including wired or wirelesscommunication channels and over any number of computer networks. Thecommunication of data between the sensor 307 and receiving unit may bevia a direct wireless short range communication channel, or indirectlythrough a wireless local area network (LAN), public switching center,router, or other public network located outside the house. Within thedamage detection data sent by the sensor 307, may be data indicating thelocation of the impact based on the location under the roof at which thesensor is installed. This location data may be programmed into andstored within the sensor during or after installation of the sensor 307.Also, more specific roof damage location may be determined by using anelectrical grid installed underneath the shingles of a roof creating anelectrical connection between each of the shingles. If an impact sensordetects damage, then the particular shingle damaged may be located bydetermining if and where there is a break in the electrical connectionbetween the shingles. This break in the electrical connection may bedetected by a sensor that receives radio frequency identificationsignals from each shingle in the electrical grid. If an RFID signal isno longer being detected by one of the shingles after the impact wasdetected, then it may be determined that that shingle was damaged.

Other damage detection systems and/or sensors 411 (e.g., water damagesensors, electrical system damage sensors, noise sensors for pestdetection, gas leak sensors, radiation sensors, sensors to detect motionof the house during a natural disaster, water pressure sensors, sonarsensors, light sensors to detect creosote buildup, etc.) may also beinstalled within the house that are operable for communicating damagedetection data to the receiving unit for collection, interpretation andtranslation of the communicated damage detection data from the otherdamage detection systems and/or sensors 411.

Referring next to FIG. 5, shown is a block diagram illustrating aportion of an example system extending outside the house for automatedhouse damage detection and reporting. Shown is the customer house 501,an example radio tower 505, customer mobile computing and communicationsystems 505, and insurance company systems 503. The customer house 501,customer mobile computing and communication systems 505, and insurancecompany systems 503 may all be in operable wireless communication witheach other through any number of communication channels and/or computernetworks, one or more of which may be via a radio or cellular tower 505that facilitates the automated communications. Damage detection data maybe automatically communicated from the customer house systems shown inFIG. 4 (either from the sensors themselves 307 309 or from the receivingunit 407) to an insurance company 503 and/or mobile devices or computingdevices of the customer 505 in order to notify the customer and takeappropriate actions to prevent impending or further damage andautomatically start an insurance claim using the damage detection datareceived.

Referring next to FIG. 6, shown is a flow chart illustrating an exampleprocess within the house for automated house damage detection andreporting. First, an impact is detected 601 on the roof of a househaving a system as described above installed. Next, data is recorded 603regarding the detected impact. For example, this data may be recordedwithin a sensor itself or intermediary collection unit. This recordeddata may then be automatically sent 605 to a receiving unit that may beoperable for collecting, interpreting and re-transmitting data from aplurality or variety of different sensors within a particular house.

Referring next to FIG. 7, shown is a flow chart illustrating an exampleprocess for automated house damage detection and reporting to aninsurance company. First, damage detection data that had originated fromsensors within a house is received 701. The damage detection data isthen analyzed 703 for insurance purposes. This analysis may be automatedand may include, but is not limited to, one or more of the following:checking local weather conditions in an area surrounding the location atwhich the damage was detected, determining the extent of damage,determining whether to automatically initiate an insurance claim,determining frequency of damage detection data reports received from aparticular house, determining frequency of damage detection data reportsreceived from a particular area, determining type of damage based onweather conditions and type of damage detection data, etc.

Next an insurance rate may be adjusted and/or insurance claim initiated705 using the analysis of damage detection data. This analysis may be,for example, analysis of damage detection data received over aparticular period of time from a particular house, neighborhood or otherspecific area. Using the extent, type and frequency of damage detectiondata received, insurance rates may be adjusted 705 for the particularhouse, neighborhood or other specific area

It is noted that the foregoing examples have been provided merely forthe purposes of explanation and are in no way to be construed aslimiting of the present invention. While the invention has beendescribed with reference to various embodiments, it is understood thatthe words which have been used herein are words of description andillustration, rather than words of limitations. Further, althoughembodiments have been described herein with reference to particularmeans and materials, the invention is not intended to be limited to theparticulars disclosed herein; rather, the invention extends to allfunctionally equivalent structures, methods and uses, such as are withinthe scope of the appended claims. Those skilled in the art, having thebenefit of the teachings of this specification, may effect numerousmodifications thereto and changes may be made without departing from thescope and spirit of the invention in its aspects.

What is claimed:
 1. A non-transitory computer-readable medium havingcomputer-executable instructions stored thereon that are executed by aprocessor to: receive, at a remote system, a signal indicating potentialdamage to a structure, wherein the signal is transmitted from a sensoroperably coupled to the structure; analyze the signal; and determinewhether to adjust an insurance rate in response to the analysis of thesignal, wherein the analysis of the signal is based on a frequency atwhich signals are received that indicate potential damage to thestructure.
 2. The non-transitory computer-readable medium of claim 1,wherein the sensor is a sensor configured to detect an impact to a roofof the structure.
 3. The non-transitory computer-readable medium ofclaim 1, wherein the remote system is associated with an insurancecompany.
 4. The non-transitory computer-readable medium of claim 1,further comprising computer-executable instructions executed to receivethe signal indicating potential damage to the structure responsive tothe sensor detecting an impact exceeding a pre-determined pressurelevel.
 5. The non-transitory computer-readable medium of claim 1,wherein the remote system is a mobile device of a person associated withthe structure.
 6. The non-transitory computer-readable medium of claim1, further comprising computer-executable instructions executed toreceive the signal wirelessly.
 7. The non-transitory computer-readablemedium of claim 1, further comprising computer-executable instructionsstored thereon that are executed to receive a signal indicatingpotential damage to the structure from a second sensor operably coupledto the structure and configured to detect damage of a different typethan that of the sensor.
 8. A method for detecting potential damage to astructure, comprising: receiving a signal from an impact sensor operablyconnected to a roof of a structure indicating an impact to the roof ofthe structure; and analyzing the signal to determine whether damage hasoccurred to the roof, wherein the analysis of the signal is based on afrequency at which signals are received that indicate potential damageto the structure.
 9. The method of claim 8, further comprisingdetermining a frequency of signals received indicating the impact to theroof of the structure.
 10. The method of claim 8, wherein the signalfrom the impact sensor is received wirelessly.
 11. The method of claim8, wherein the structure is a first structure, and wherein the methodfurther comprises determining a frequency of received signals indicatingan impact to a roof of a second structure in an area proximate to thefirst structure.
 12. The method of claim 8, further comprisingdetermining a type of damage based on the analysis of the signal and aweather condition local to the impact sensor.
 13. The method of claim 8,further comprising determining whether to initiate a process foradjusting an insurance rate based on the analysis of the signal and theweather condition local to the impact sensor.
 14. The method of claim 8,further comprising determining an extent of damage to the roof of thestructure based on the signal indicating the impact to the roof of thestructure.
 15. A non-transitory computer-readable medium havingcomputer-executable instructions stored thereon that are executed by aprocessor to: receive a signal from a damage detection sensor operablycoupled to a structure, wherein the signal indicates data associatedwith potential damage to the structure detected by the sensor; anddetermine a type of potential damage to the structure based on the data,wherein the determination of the type of potential damage is based on afrequency at which signals are received that indicate potential damageto the structure.
 16. The non-transitory computer-readable medium ofclaim 15, wherein the damage detection sensor is configured to detectelectrical system damage associated with the structure.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the damagedetection sensor is a noise sensor configured for pest detection. 18.The non-transitory computer-readable medium of claim 15, wherein thedamage detection sensor is a gas sensor.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the damage detectionsensor is a water pressure sensor.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the damage detectionsensor is configured to detect creosote buildup.